Common carrier system

ABSTRACT

An on-line system and method for buyers and sellers of international container transportation services is disclosed. Specifically, the system offers importing and exporting customers the opportunity to request and select specific service patterns offered by participating carriers in the booking of full container shipments. The system includes user interfaces that allow a shipper to track and trace containers across multiple carriers and an event notifications system, which notifies the user when an event has or has not occurred.

RELATED APPLICATIONS

This application claims priority to provisional application U.S. Ser.No. 60/238,454, filed Oct. 10, 2000, whose contents are expresslyincorporated by reference.

BACKGROUND OF THE INVENTION

Today, shipping goods is a complicated business. Carriers have a finiteamount of cargo space, and accordingly, shippers often negotiate withmultiple carriers to coordinate the movement of just one container.Typically to limit the uncertainty and cost of moving goods, shipperscontract with multiple carriers to provide a predetermined volume ofbusiness to each carrier at an agreed upon rate. This gives shippers theflexibility to choose from a number of different carriers to transportgoods (for example, shipping directly from Stockholm to New York, ratherthan through an intermediate location) and increases the likelihood ofmoving a container when the shipper needs the container moved whileguaranteeing individual carriers a volume of business. In practice, ashipper sequentially contacts carriers to check availability. If onecarrier doesn't meet the shipper's desires, the shipper then contactsanother contracted carrier. For example, refrigeration may be requiredand only certain carriers may handle refrigerated goods, the shipper maynegotiate with only those contracted carriers that providerefrigeration. Even if the carrier may handle refrigerated cargo, theymay not have the cargo space available to move the goods by a given day.Accordingly, even if the shipper and carriers have executed a contractprior to negotiations to move goods, shippers are still effectivelyrequired to negotiate with multiple carriers when securing the transportof cargo.

Since shippers typically contract with multiple carriers, the shipper isrequired to learn and understand a variety of different carrieridiosyncrasies. The differences between carriers is compounded as eachcarrier attempts automation and/or direct booking over the internet.Each carrier booking system (or platform) may be different in the lookand feel as well as in the process that one requests the transport ofgoods. This forces each shipper to learn each carrier's platform toeffectively and efficiently book a shipment of goods. The entire processis both confusing and time consuming for shippers. Carriers are thenfaced with incorrect or irreconcilable booking reports leading to morelost resources.

Freight forwarders add yet another level to this complicated business.Freight forwarders generally coordinate the transportation of goods onbehalf of the shippers. For example, if the shipper desires goods beshipped from Chicago to Tokyo, the freight forwarder, on behalf of theshipper, negotiates and/or coordinates with the carriers to arrange forthe goods to be moved. Essentially, the freight forwarders provideshippers with a service and generally do not move the goods themselves.Thus, freight forwarders provide shippers with an alternative tocoordinating transportation of goods with the carriers. Although,freight forwarders provide shippers with a valuable service, they alsocreate inefficiency and increase shipping costs for shippers as the costfor the service of the forwarders is billed to the shippers.

Biasing results in yet another inefficiency. Forwarders may receiveincentives to direct business to certain carriers over others. Also, asthe complexity of the shipping business creates a desire for bothshippers and freight forwarders to contract with certain carriers, thisdesire naturally creates a bias towards the contracted carriers. Forexample, if a shipper wants to move goods from Detroit to Spokane, theshipper may negotiate with a contracted carrier which only moves goodsdirectly to Seattle. A second carrier would be needed to complete thetransport from Seattle to Spokane, thus, requiring an additional leg tomove the goods to Spokane. However, if the shipper wasn't biased towardsthe contracted carriers, the goods may have been shipped directly toSpokane using a non-contracted carrier. Accordingly, shippers or freightforwarders may be creating inefficiencies by not using all availableresources.

Since shippers or freight forwarders typically move goods using avariety of carriers, tracking and tracing goods across differentcarriers is also costly. Because shippers or freight forwarders oftencoordinate transportation of goods with multiple carriers, they arerequired to learn how to track and trace goods according the specificcarrier's platform. Since shippers may have hundreds of containers beingshipped by many different carriers at any given time and want to knowthe status and related info for their shipments, both shippers andcarriers devote large amounts of resources to tracking and tracingcontainers. It is not uncommon for carriers to devote an entireworkgroup to handling phone calls from shippers requiring information onthe location of their goods. A consolidated system is needed thatpermits shippers to track shipments from a variety of carriers. Also, asystem is needed that permits tracking of a shipment across multiplecarriers.

In recent years developers have used the internet to create virtualmarketplaces that bring together buyer and sellers, run negotiations andgive companies and their suppliers the ability to readily shareinformation. Some attempts have been made to reduce the cost to theshipper by using the internet. One attempt was to give carriers theability to post published rates and discount information for land, seaand air bearing cargo vessels allowing customers to evaluate pricesprior to booking. Another attempt to use the internet, give shippers theability to receive a plurality of bids from a plurality of participatingcargo transportation entities. These systems merely identify the cost ofdoing business with a select carrier and no more. This does not solvethe problem of having to use multiple carrier platforms to submit thebooking request to different carriers. This also does not permit easyexchange of goods between carriers where multiple carriers are used fora single shipment.

Finally, warehousing goods, transporting goods, customs brokerage andtrade finance are complicated pieces of a very complicated business.Accordingly, a need exists for a more efficient system for handlinglogistics and transportation of goods.

SUMMARY THE INVENTION

The disclosure provides a method and system that enables domestic andinternational transportation users to handle shipping transactionsthrough a single common system through a neutral transportation portal.The system provides, among other things, transportation users withsingle point of entry for tracking cargo movements with multiplecarriers. In various embodiments, the system also gives users access toscheduling, booking requests for booking cargo across several carriersand, in some embodiments, proactive event notification.

These and other benefits will become apparent as described in thedrawings and related description.

BRIEF DESCRIPTION OF DRAWINGS

FIGS. 1 a and 1 b illustrate the system infrastructure according toembodiments of the present invention.

FIGS. 2 a, 2 b, 2 c, 2 d, 2 e, 2 f and 2 g illustrate a flowchartdepicting a booking process according to embodiments of the presentinvention.

FIG. 3 illustrates an example of a selection screen according toembodiments of the present invention.

FIGS. 4 a-4 c illustrate an example of a booking request screenaccording to embodiments of the present invention.

FIG. 5 illustrates an example of a contact section of the bookingrequest screen according to embodiments of the present invention.

FIG. 6 illustrates an example of the HAZMAT screen according toembodiments of the present invention.

FIG. 7 illustrates an example of the temperature control screenaccording to embodiments of the present invention.

FIGS. 8 a, 8 b, 8 c and 8 d illustrate an example of haulage and searchscreens according to embodiments of the present invention.

FIGS. 9 a and 9 b illustrate an example of company search screensaccording to embodiments of the present invention.

FIGS. 10 a and 10 b illustrate an example of a search template screenaccording to embodiments of the present invention.

FIG. 11 illustrates an example of a search for a booking screenaccording to embodiments of the present invention.

FIGS. 12 a, 12 b and 12 c illustrate examples of track and trace screenand result screen according to embodiments of the present invention.

FIG. 13 illustrates an example of the common carrier system according toembodiments of the present invention.

DETAILED DESCRIPTION OF THE EMBODIMENTS

The following description is divided into sub-sections to assist thereader. The sub-sections include: terms; infrastructure; booking processand user interface; track and trace; and event notification.

Terms

The following terms are used in the description.

Shipper—Any entity with goods to be transported. The entity may desirethe goods be transported or may be transporting the goods for adifferent entity.

Freight forwarder—An entity that coordinates the transportation of goodswith a carrier or carriers for a shipper.

Carrier—Any entity that transports goods from an origin to adestination. The carrier may transport goods domestically and/orinternationally. For example, a carrier may transport goods for ashipper from Chicago to Seattle or the same carrier may transport goodsfrom Chicago to Paris. The carrier may transport goods using trucks,trains, planes, ships, and/or the like.

Carrier Platform—A carrier's computer system supporting an interfacethat enables exchange of information with the carrier.

Common Carrier System—Infrastructure that supports the common carrierinterface including data storage.

Common Carrier Interface—An interface that enables multiple users andmultiple carriers to communicate.

User—Any entity that uses the common carrier system. All users may havevarious levels of interest in using the common carrier system. The mainusers of the common carrier system may be shippers, third-partylogistics providers, freight forwarders, consignees, brokers, tradingportals, carriers and the like.

Booking—A reservation to transport a volume of goods from a singleorigin to a single destination. The goods may vary in product type, maybe a mix of hazardous and non-hazardous, may require refrigeration andthe like. The booking may be a single booking or may be repetitive.

Routing Request—A query to the carrier to determine if the carriersupports the basic transpirations of the cargo as part of the carrierproduct catalog.

Booking Activity Plan—A carrier plan that encompasses the major, ormilestone, activities of a shipment.

Infrastructure

FIG. 1 a illustrates an example of representative infrastructureaccording to embodiments of the present invention. The user 101 a-101 e,via terminals, communicates with a plurality of different carriers 103through the common carrier system 102 including server(s) 102 b-102 cand database(s) 102 a. In one embodiment, users use terminals toexchange information with the common carrier system 102. These terminalsmay be standard personal computers as are known in the art (forinstance, a computer system using a PENTIUM III processor). Inalternative embodiments, the users may use hand-held or other portabledevices as known in the art to communicate with the common carriersystem 102. Further, the communications from multiple users may bebatched together at a user's location prior to transmission to thecommon carrier system 102. Although FIG. 1 a shows five users, fivecarrier terminals, one database and three servers, FIG. 1 a is merelyillustrative and the number of, users and/or user terminals, carriersand/or carrier terminal, servers and databases is not in anyway limited.Furthermore, although the embodiments are described in the context of asingle system, one of ordinary skill in the art may appreciate that thedescribed functionality may be implemented across multiple systems.Moreover, a web site may be mirrored at additional systems in thenetwork and, if desired, one or more management systems or othercomputer resources may be used to facilitate various functions. Thecomputer program at the system includes appropriate screen routines forgenerating a set of screens that together comprise a user interface forthe site.

Referring to FIG. 1 b, illustrates, in more detail, the common carriersystem 102. The common carrier system includes, for example and withoutlimitation, servers 104 a-104 c. Server 104 a includes mail server 105which may be used to receive and send data via email. Server 104 a alsoincludes server 106 for receiving and sending data over the internet.Server 104 b includes server 107 as a communication bridge betweenserver 108 and servers 105 and 106. Server 107 polls servers 105 and 106for new messages, unpacks and sends the messages to server 108. Foroutbound polls from server 107, server 108 adds the receiver's addressand triggers the transfer of the message. When server 107 fails toprocess an EDI message, an email will be sent to a predefined emailaddress. Server 108 processes EDI messages by validating the data whencalled by server 107 and translating the data into the common carriersystem layout format. For outbound EDI messages, server 108 is called byserver 109 and server 109 feeds server 108 with the outbound EDI messagein the common carrier system layout format. Server 104 b includesservers 109 and 110. Server 109 converts and loads common carrier systemlayout to a set of database tables, or vice versa. Server 109 also pollsserver 108 for any new messages, opens a connection to the database andpopulates the database tables corresponding to the EDI message type(300, 301, 315 and the like, show in FIG. 13). For outbound EDImessages, server 109 scans the database tables populated by an EDIprocessor and converts the message and then triggers server 108 toprocess the common carrier layout format. Referring to Server 110, theEDI processor is part of the server 110 that processes the EDI messagesdeposited into the database tables by 109. Server 110 scans the headerof the database table for the first unprocessed message being marked forexample as submitted. The status is then change from submitted toprocessing in the database 111 and if successful the status is thenchange to complete.

The present disclosure relates to a system and method for buyers andsellers of domestic and/or international transportation services relatedto the shipment of goods. The users and carriers may be linked to thesystem by dial-up modem to communicate to the internet, and accordingly,be disconnected from the system or off-line. For example, the user mayuse a dial-up modem and submit a booking request to a carrier throughthe internet and afterwards disconnect from the internet. After the userdisconnects and is currently off-line, the common carrier system maysubmit the booking request to the carrier and receive confirmation ofthe booking request from carriers while the user is off-line. In anotherembodiment, the common carrier system 102 may process the informationwhile the user is still connected with the internet. This permits theuser to be notified as soon as availability is determined for variouscarriers or after a reservation has been made with the carriers by thecommon carrier system 102. The system and method offers shippers theopportunity to request and select specific service patterns offered byparticipating carriers in the booking of full container shipments. Thesystem and method includes user interfaces, processes, computer systems,and computer-readable mediums having programs stored thereon. The systemand method enable a user to submit booking requests to multiple carriersand/or track and trace the goods using a single common carrier systemand interface. The system and method also may be used to provide eventnotification.

In general, when a shipper wants to move goods, the shipper submits abooking request to one or more carriers to which the carrier(s) respondsby accepting, rejecting, or changing the booking request. A bookingrepresents a shipper's intention to transport a volume of goods from asingle origin to a single destination. The goods may vary in producttype, may be a mix of hazardous and non-hazardous, may requirerefrigeration and the like. As a result, differing container types maybe required. To accommodate differing cargo characteristics, a bookingmay contain one or more booking lines. The request may be made using avariety of different processes. The user 101 may send an email messageto the common carrier system 102, who processes the email and acts inresponse. Alternatively, the user 101 may post information to a web siteof the common carrier 102. Further, the user 101 may transmitinformation in the form of XML or EDI data sets for processing by thecommon carrier system 102. It is appreciated that a number of differenttransmission schemes may be used to forward requests to the commoncarrier system 102. The information received by the common carriersystem 102 may then forward the requests to a variety of carriers 103.The common carrier system 102 may blindly forward the request to allcarriers 103 to see who responds. Otherwise, the common carrier systemmay filter the booking request from user 101 to minimize the number ofcarriers 103 who receive the request. In addition, the common carriersystem 103 may have a routing list as specified by the user forpermitting the ordering of the hierarchy in which carriers are polledfor booking availability.

The transmissions between the common carrier system 102 and the carriers103 may also be in the form used by the user. Alternatively, the commoncarrier system 103 may translate the user's request from one form orformat into one understood by the carrier or carriers 103. If needed,common carrier system 103 may add information or subtract information asneeded for each carrier 103. For example, some carriers may use one typeof units while others use another type of units. The common carriersystem 103 then translates the units provided by the user for submissionto the carrier. Also, the user may have certain needs if goods aretransported one way as opposed to another (refrigeration needed ifshipped in a container ship while no refrigeration needed if shipped bytruck or train). If so, the common carrier system 103 may eliminate ormodify the information transmitted to each carrier 103 so as to meet theneeds of each carrier's platform and/or booking system. A booking linemay include a single container type, single hazardous goods indicator,single refrigeration and a single commodity description. When the commoncarrier system receives the first carrier booking confirmation massage,for example the confirmation from carrier 103 a, the system 102 may,upon the shippers request (any user using one of terminals 101 a-101 eor other known devices like, for example, a mobile PDA), automaticallygenerate and submit booking cancellation to other carriers 103 b-103 e.

Alternatively, the booking request from the common carrier system 102may request information from the carriers 103 of who has availabilityfor handling the proposed booking. The response from the carriers 103provides the common carrier system 102 with information of availability,shipping time frame, and other information.

In one example, an interested party, typically the shipper or freightforwarder, enters a booking draft with high-level details about thefreight it desires to be shipped. Using the information entered on thebooking, the user of the system may also, via terminals 101 a-101 e,issue a routing request through the common carrier system 102 to one ormore carriers 103 a-103 e. One or more of carriers 103 a-103 e respondswith detailed routing information. The shipper may request the carrier103 a-103 e submit routing information based upon the data containedwithin the booking (place or receipt, place of delivery, etc.) Thecommon carrier system 102 enable users (via terminals 101 a-101 e or byother known devices like, for example, a mobile PDA) to submit abooking, with or without a routing request, and it may be submitted toone or more carriers 103 a-103 e.

The actual interfaces between the user 101 and the plurality carriers103 handling the routing request may be determined by the technicalcapabilities of the carriers 103. Sophisticated carriers 103 may providedirect online response through their internal systems. Other carriers103 may use the service patterns interface to store available routings.At a minimum, all carriers may respond to routing request via using thecommon carrier system 102. Separate confirmation directed to each usermay also be made (via email, instant messaging and the like).

If the booking party 101 chooses to so specify (for example, by checkinga checkbox or similar object on the booking screen), the first carrierto respond with a valid response to the routing request mayautomatically be selected and the booking may be submitted to thecarrier. Otherwise, the booking party may manually select the carrierand submit the booking. It is now up the carrier to determine if theactual transport of cargo may take place (based on vessel capacity,equipment availability, etc.) and either confirm the booking, declinethe booking or make a counter proposal.

Referring to FIG. 1, after carrier 103 a confirms the booking, the usersends shipping instructions using the common carrier system 102 byinteracting with the common carrier interface. The information sentcontains more details about the freight, such as hazardous/refrigerationcharacteristics. Since the booking already contains the rudimentaryinformation about the care, the shipping instruction don't need tohappen at any a particular time. The carrier then sends the bill oflading based on the shipping instructions.

Finally, when a carrier confirms the booking, the carrier may return abooking activity plan as part of the booking confirmation. The plan maybe stored in the common carrier system database(s) 102 a of the commoncarrier system 102 and subsequent track and trace messages may be usedto measure performance (time to process bookings, per cent on timedelivery, claims, misdeliveries, etc.) against the booking activityplan.

The common carrier system enables the common carrier interface providesthe users with a unified booking interface and procedure while alsoproviding an additional source of bookings for the carriers.

Furthermore, the common carrier system and interface enables the user tocreate templates tailored for their specific needs. Accordingly, theuser may quickly create template-driven booking requests without havingto step through the entire booking process. Also, Identifying andregistering a user's consignees, forwarders, shippers, et al., mayfacilitate the template building process and provide shipment visibilityto user's partners as quickly as possible.

Booking Process and User Interface

The description of the first embodiment is organized to show processflows as taken by the user. Various user interface screens embody theprocess flows. FIGS. 2 a-2 g illustrate the booking process fromcreating a booking request, using any one of the three booking methods,through receipt of booking confirmation. FIGS. 3-12 illustrate thevarious screens the user may encounter throughout the booking processdescribed by FIGS. 2 a-2 g. Although, FIGS. 3-12 illustrate displayscreens, the particular screen layouts are used for exemplar purposesonly and should not be taken to limit the scope of the embodiments inany way.

The process of creating a booking request through confirmation will nowbe described, with reference to FIGS. 2 a-2 g. The process may berearranged as needed or to accommodate faster information processing.Referring to FIG. 2 a, first the user logs into the common carriersystem as shown in step 201. At step 202, the user selects a new bookingrequest. At steps 203-205, the user chooses from creating a new bookingrequest, reusing an existing booking request and creating a bookingrequest from a predefined template.

Creating a new booking request will now be described. If the userchooses to create a new booking request in step 203, then the usercontinues to step 206 and identifies the carrier and the commoditydescription details. If HAZMAT data is not desired, the user advances tostep 210 of FIG. 2 b. If HAZMAT data is desired, the user enters thedata at step 208 via a pop-up window and then advances to step 210.Optionally, the user may enter contract information at step 209 in afree text field.

Referring to FIGS. 2 b and 2 e, at step 210, the user identifiesequipment quantity and type. If specific environmental conditions arenot desired, the user continues to step 213. If certain environmentalconditions are desired, at step 212, the user enters the appropriatedata and then advances to step 213. At steps 213-215, the useridentifies the place where the carrier responsibility for cargo beginsincluding the pick-up date and the place where carrier responsibilityfor cargo ends including the delivery date. Optionally, the user mayenter the load location and discharge location and/or specialinstructions in steps 216 and 217.

Referring to FIG. 2 f, from steps 215 or 217 and if door pick-up isdesired, the user advances to step 218. If not, the user advances tostep 220, door drop-off. From step 220, if door drop-off is not desired,the user advances to step 226. If door pick-up is desired, the useridentifies the address, any necessary comments, and dates at steps221-223. The user then continues to step 220. If door delivery isdesired, the user identifies the delivery address and the date forcontainer delivery during steps 224 and 225, respectively.

Referring to FIG. 2 g, from steps 220 or 225, the user advance to steps226, and if desired, step 227. The user identifies the shipper and othershipment parties, step 226. The shipper may be the booking party. If theother shipment parties are not registered, the system may not providevisibility. However, the system may provide booking visibilityimmediately to registered parties, steps 227-230.

After identifying the shipping party at step 236 and steps 227-230, theuser advances to step 231 and submits the booking request to the system,wherein the system submits the booking request to the carrier at step234. The user may also reach step 234 by entering a reference number andremarks during steps 232 and 233, respectively. Additionally, the usermay reach step 234 by reusing an existing booking request or from apredetermined template as shown in FIG. 2 a, steps 204 and 205. The useridentifies the old booking or the template and then updates the routing,haulage, dates and submits the updated booking request, steps 235-240.Furthermore, the common carrier system enables entities to register viathe common carrier interface.

Referring to FIG. 2 c, the carrier may be alerted by the common carriersystem, via Electronic Data Interchange (“EDI”), email, common carrierinterface pop-up dialogue box and the like, step 241. CSR enters thebooking into the carrier's booking system and confirms or counters thebooking origin, POL, POD, destination, load date, discharge date, vesselvoyage and the like in the common carrier system, steps 242-244. If doordelivery was requested, the CSR enters carrier outbound container P/U,if not, the CSR enters cutoff date at origin in the common carriersystem, steps 245-247. The booking is confirmed, countered or rejectedand returned to the common carrier system. The common carrier systemalerts the user of the reply from the carrier, steps 248-249. The usertakes no action, and thus, accepts the booking as is, cancels thebooking request or amends the booking request, steps 250-252. If theuser cancels or amends the booking, the carrier is alerted and accepts,declines or changes the booking in the carrier system and updateschanges in the common carrier system. The common carrier system submitsthe response to the user via EDI, email, common carrier interface pop-updialogue box and the like, steps 253-256.

As illustrated in FIGS. 2 and 3, the user, after login, has a number ofoptions to navigate through the common carrier system. To create a newbooking request, the user selects the “Booking” menu option 301. Thismenu option enables the user to create a new booking request 302 orsearch for an existing booking request 303. If the user needs to createa new booking request, then the user has three options: (1) create a newbooking request from scratch 304, (2) reuse an existing booking request306 and (3) create a booking from a predefined template 305 as shown inFIG. 3.

Creating new booking request will now be described with reference toFIGS. 3-10. Upon selecting the “from scratch” menu option 304, shown inFIG. 3, the user is linked to the new booking request screen, shown inFIG. 4 a-4 c. The new booking request screen is divided into severalsections: (1) carrier selection 401, cargo information 402, containerinformation 403, routing information 404, booking parties 405 a-405 d,and additional information 406. Each enables the user enter information.Although all sections are shown on a single screen, this is merely anexample and should not be taken to be limiting in any way. For example,each section maybe shown using a separate screen. Each of these sectionswill now be described with reference to FIGS. 4-9.

FIG. 4 a shows the carrier selection section 401 of the booking requestscreen. To enter information in this section, the user clicks the“Select Carrier” drop-down menu 407 and identifies which registeredcarrier may be sent in the booking request. If desired, the user mayenter a contract reference, the quote number or TLI in the contractreference field 408. Optionally, the user may enter a PO number into thePO number field 409. If desired, the user may attach additionalreference numbers by clicking the “Additional Reference Numbers” button410 which would link the user to the additional reference screen asshown in FIG. 5. The user may enter a reference type by using adrop-down menu 501. Also, the user may enter a reference value in thereference value field 502, add a reference by clicking the “Addreference” button 503, and/or may remove reference(s) by clicking the“Remove Reference” button 504. After the user has entered theappropriate data for each object, the user clicks the “Done” button 505.

Referring to cargo section 402 of FIG. 4 a and FIG. 6, the user mayenter the commodity description in the description field 411, along withthe total cargo weight in the total cargo weight field 412. The userdefines the total cargo weight as being either metric or imperial usingdrop-down menu 413. If the commodity is hazardous, the user may clickthe “Hazmat” button 414. This button links the user to the hazardousmaterial settings window shown in FIG. 6. The common carrier systemsupports multiple hazardous IMO classes per commodity. For example, acommodity “Car Parts” may hold two hazardous line items, one for seatbelt tensionless, and another for air bags. The user selects theappropriate hazardous class from the “IMO Class” drop-down menu 601 andthen user enters the proper shipping name and the four digit UN numberin the un number field 602. Additionally, the user may enter the packinggroup, flash point, emergency contact details and further specificationfor each IMO line item in fields 603-606, respectively. Once all thedetails for one IMO class have been entered, the user clicks “Add IMOClass” button 607 to associate the hazmat details with the commodity.After the user is finished inputting of the hazmat details for all thecommodities the user clicks the “Done” button 608.

Referring to the container information section 403 of FIG. 4 a and FIG.7, the user enters the number of containers they wish to request in thequantity free text field 414. With the “Type/Size” drop down menu 415,the user identifies the kind of equipment they wish to request. Somecarriers do not support some types of equipment. To help the user,carrier-specific equipment may be identified in the drop down free textliterals. The user identifies at least one container for each bookingrequest. In the container information section, the user has the optionof selecting the “Temperature Control” button 416 to bring up therefrigeration details pop-up window as shown in FIG. 7. The user may setthe booking temperature as Fahrenheit or Centigrade by clicking the ° C.or ° F. buttons 701 and 702, respectively; set the temperature usingfield 403 and clicking either button 404 or button 405; set theventilation in cubic meters per hour using field 706; set the humiditysettings as a percentage using field 707; and provide additionalcomments using field 708. After enter the appropriate setting, the userclicks the OK button 709 to save the environmental settings.

Referring to the routing information section 404 of FIG. 4 b and FIGS. 8a, 8 b, 8 c, and 8 d, the user enters the routing details for thebooking request. The user enters the place of origin in field 417 (placeof origin is the location where the carrier's responsibility for thecargo begins); the requested date at origin in fields 418 a-418 c (thedate when the carrier takes responsibility for the cargo); the requestedvessel voyage in field 419; and the destination in field 420 (thelocation where the carrier's responsibility for the cargo ends).Optionally, the user may enter the load and discharge locations infields 421 and 422. If the user desires to have the product picked-up,the user clicks the “Door Pickup” button 423 which links the user to thedoor pickup details screen shown in FIG. 8 a. The user then enters theoutbound empty equipment drop-off date and time in fields 801 a-801 d,the outbound stuffed equipment pick-up date and time in fields 802 a-802d, and additional door pick-up details, including company name, contactdetails, telephone, and the pick-up address in fields 803-806,respectively. After entering the appropriate information, the userclicks the “Save Haulage” button 807 to update. Additional haulagedetails may include hot load, equipment drop-off schedules and the like.If the user desires to have the containers delivered, the user clicksthe “Door Delivery” button 424 which links the use to the haulagerequirements delivery screen shown in FIG. 8 b. The user enters theinbound empty equipment availability date and time in fields 808 a-808 dand additional door pick-up details, including company name, contactdetails, telephone, and the pickup address in fields 809-812,respectively. Followed by the user clicking the “Save Haulage” button813 to update. Additional haulage details may include hot load,equipment drop-off schedules, and the like.

Optionally, the user may search to find the common carrier system forthe registered locations of the place of origin, load and dischargelocations. Several locations in the booking screen may be registered(non-free text) locations. To assist the user with identify theselocations, the user may link to the search screen for assistance byclicking any of the buttons 425-428. The user may enter any combinationof city, state, and country in fields 814-816 and press the searchbutton 817 of FIG. 8 c. The common carrier system displays the resultsshown if FIG. 8 d. The user clicks on the correct location to select it,for example click on line 818, 819 or 820, or clicks the “Start Over”button 817 to return to the search screen.

Referring to the booking parties section 405 of FIGS. 4 b-4 c and FIGS.9 a, and 9 b the user enters the booking parties, thus, identifying theparties associated with the booking request. The booking party may beidentified as any one of shipper, export forwarder, consignee,contracted party and the like. Either the shipper or the exportforwarder is identifiable on the system. To receive cargo visibility assoon as possible, the identified parties may be registered on the commoncarrier system. The parties may register with the common carrier systemusing the common carrier interface. If booking parties are not selectedin this section, they may not be able to view the booking until theircontact information is retrieved from the BL. That is, booking partiesidentified by the user may be capable of viewing the booking so long asthey were a party selected by the user and they are registered with thecommon carrier system. Registration may be completed using the commoncarrier interface. Using fields 429 a-429 d, 430 a-430 d, 431 a-431 d,432 a-432 d and 433 a-433 d as shown in FIGS. 4 ba and 4 c, the user mayenter the name, address, reference, contact, and telephone number of thebooking parties. So long as the party is registered, that party may viewthe booking.

FIGS. 9 a and 9 b show a company search window for the user'sconvenience. When the user clicks the “Search” buttons 434 a-434 d fromany booking party section, the user is linked to the company searchpop-up window. The user enters the company name in the window in field901 and clicks the “Search” button 902. The user then clicks on thedesired company. An example list is shown in FIG. 9 b.

Referring to the additional information section 406 of FIG. 4 c, ifdesired, the user may provide additional information by entering theadditional comments in the additional information field 435. This areais free text and may hold, for example, details not be captured in theexisting booking screens. Comments, for example, may include drop andpick; hot load, drop-off/pick-up schedules, HAZMAT details and the likeshould be entered here.

Once the user entered all initial data, the user may send the bookingrequest, save the booking request as a draft or save the booking requestas a template by clicking one of the appropriate buttons 436-438. If theuser sends the booking request, the carrier selected by the user maythen be alerted by the common carrier system and reply to the user'sbooking request. If the user saves the booking request as a draft, theuser may at a later time complete the booking request and send it to thecarrier and/or save the booking request as a template.

Creating a booking request from a template will now be described.Referring to FIGS. 10 a and 10 b, to create a booking request from anexisting template, the user starts from any of the common carrier systemscreens after login and selects the “New” 302 menu and then the “FromTemplate” menu 305 from the booking menu 301 as shown in FIG. 3. Thisaction links the user to the template search screen. The user enters atleast one of the template name, origin/destination, cargo description,company, and carriers in fields 1001-1006, respectively, to find thebooking template. Once the user enters the data, the user clicks the“Template Search” button 1007. The common carrier system generates alist of any template that matches the search. The user selects thedesired template. An example list is shown in FIG. 10 b. If desired, byclicking the “New Template Search” button 1008, the user may add orremove criteria to limit or broaden the search. Once the user finds theappropriate template, the user may, for example update the datesassociated with the booking along with additional booking requestfields. The user may save the template and/or submit the booking requestto the carrier. If desired, the user may delete the template, forexample, by checking a box, like 1010, and clicking the “DeleteTemplate” button 1009.

Reusing an existing booking request will now be described. Referring toFIG. 3 and FIG. 11, starting from any of the common carrier systemscreens after login, the user select the “New” menu 302 and then “FromExisting Booking” menu 306 from the booking menu 301 of FIG. 3. Thisaction links the user to the search booking screen shown in FIG. 11. Theuser inputs data in at least one of references, booking number, oceancarrier booking number, bill of lading number, container number, bookedvessel, booked voyage, latest vessel, latest voyage, cargo description,location, dates, company, carriers, cargo and event fields 1101-1112,respectively. The user selects the desired template from the returnedlist of old bookings, or performs another search. Once the user findsthe desired booking request, the user updates the booking and submitsand/or saves the booking request.

The common carrier system is capable of developing forms for the commoncarrier interface which help users capture their tradelanes, commodityand equipment requirements, routing, and booking party details. Theseforms enable the common carrier system to create customer specificbooking request templates. In most cases, a booking template capture themajority of fields described above, and worksheets group these fieldsinto easily understood sections.

Bookings may be made, for example, through the common carrier systemuser interface, Electronic Data Interchange and the like. EDItransmission pass through the common carrier system to allow commoncarrier system functionality to be used. For example, track and tracefunctionality require the booking EDI transmission pass through thecommon carrier system. Booking made via the common carrier system userinterface may be made from scratch of facilitated by means of previouslysaved data in the form of templates or previous booking as describedabove.

Track and Trace

This embodiment enables the user to track and trace only by identifyingcontainer as opposed to tracking and tracing by identifying both carrierand container. That is, the user does not need identify which carrier istransporting their container. Accordingly, the common carrier systemenables the user to track and trace containers across multiple carrierplatforms from a single system, the common carrier system.

The common carrier system facilitates track and trace information withinthe confines of a carrier's responsibilities. The boundaries fortracking a shipment directly reflect the associated route and servicepatterns supporting that container's movement. Applicable common carriersystem users, via terminal 101 a-101 e of FIG. 1, have the ability toview the execution status of the shipment(s) on an as-needed basis. Thebooking activity plan defines the carrier's intended method and timesfor transporting a container from its origin to its final destination.This provides the benchmark for determining whether events that shouldhave occurred have not. The common carrier system 102 alerts the partiesof non-confirmation. The carriers offer event reporting against themilestones contained in the booking activity plan. The system operatesusing standard event codes and standard event messages. In other words,carriers 103 may update the common carrier system 102 using commonreporting information. Alternatively, the common carrier system 102 mayreceive tracking information from each carrier in each carrier's nativereporting format. The common carrier system 102 then extracts desiredinformation from the carrier's tracking information and formats it intoa style that is extensible to the user 101. Also, an intermediate formatmay also be used to internally store the tracking information from eachcarrier in the common carrier system 102. The system may log when eventmessages are received (in local time) to enable carrier performancemonitoring.

To use the track and trace function, the user request a booking with acommon carrier registered carrier using the common carrier system asoutlined above. The carrier confirms the booking request and submits abooking activity plan for the booking at the same time. A single bookingsupports a single booking activity plan. The booking may consist ofmultiple container movements. The booking activity plan may be used tosupport track and trace information at the container level. The bookingactivity plan may provide greater information than a service pattern,since each main leg may be broken down into actual transport modes,transshipment locations and interim arrival and departure date/times.

Once the carrier submits the booking activity plan the container may betracked and traced. The carrier submits the track and trace events tothe common carrier system either by EDI or via a common carrier systemuser interface. Carriers may continue to use their own coding conventionwhen submitting events by using EDI translator. EDI translatortranslates carrier event codes and message formats into a common carriersystem neutral format. The common carrier system may record when ashipment has departed and arrived at the various location and recordwhen business processes or non-conformances occur. The common carriersystem may also record the date and time when the common carrier systemreceives track and trace events. The date and time recorded by thesystem maintains consistency with the date and time associated withwhere that event occurred (e.g. from GMT to local time of the shipper,local time of the destination location, local time of the sendinglocation, and the like). That is, the date and time may be adjusted tomatch the time zone of the user or other parties.

The user uses the track and trace function by using the common carriersystem track and trace user interface. This enables the user to selectcriteria against which a search may be conducted. The user has theability to customize how the search results are displayed. The user hasthe ability to customize display results on an individual containerbasis or on a “batched” container basis. The common carrier system may“batch” container records. When the common carrier system returns trackand trace information on “batch” records, the user has the ability todrill-down to the container level detail and to drill back up.Furthermore, the user has the ability to ascertain, at glance, where thecontainer is in relation to the activity plan and clear visibility as towhat events have been successfully completed and which were not.

Referring to FIGS. 4 a and 12 a-12 c, by clicking, for example, thetrack and trace icon 436 of FIG. 4 a, the user enables the track andtrace search window as shown in FIG. 12 a. The user enters the specificcontainer data in the field 1201 and, by using the drop-down menu 1202,the user identifies the type of data. The type of data may be any of thefollowing: bill of lading number; container number; booking number;carrier booking number; customer reference number; shipper/consigneenumber, date ranges for place of receipt, first load port, finaldischarge port and delivery location; receipt/delivery locations,load/discharge locations, carrier, vessel and voyage number, currentcontainer activities/status and the like. The common carrier interfacedisplays the search results screen as shown in FIG. 12 b. If desired,the user may view a booking summary by clicking on, for example, theword “details” 1203 or track the containers by clicking on the “TrackContainer” button 1204 which links the user to the container plan screenshown in FIG. 12 c. Furthermore, the user has the option of customizingthe booking by clicking the “Customize Booking” button 1205.

Event notification may be submitted to the nominated users using any ofthe following technologies: EDI, Email, common carrier interface pop-updialogue box and the like. This may be based on the users technology.Furthermore, the user may define the rules with respect to eventnotification. Table I below shows an example of the events, eventtriggers and event notification as determined by the user.

The system may, upon the user demand, automatically generate notices ofcargo movement according to the user specification. The event handlingfunctionality may be employed to provide notification regarding thecertain track and trace events, track and trace non-events, and certainbusiness process decisions. The event notification component of thecommon carrier system may reflect the workflow environment wherebyinterested users are notified when an event has occurred, or when onehasn't (e.g. a shipment was expected on a certain day, but is notexpected to arrive until the next day). The user may specify theirtolerances for these events. For example, one user may which to know ifa shipment is late more than six hours, whereas another is more tolerantand a 24 hour delay and notification is acceptable.

To notify the user when an event has not occurred, the common carriersystem polls the booking activity plan information periodically toidentify non-conformances against the booking activity plan, that is,when milestone events (that should have occurred) have not. Eventmessages may contain event code and location information. When thesystem identifies a non-conformance, an event notification isautomatically generated and submitted to nominated entries. Anon-confirmation in this case is deemed to be when the system has notreceived an event message prior to or at the date/time of the eventshould have occurred as defined in the booking activity plan. The commoncarrier system also submits track and trace events notifications whencertain “optional” events are notified to the system, for examplecustoms held and customs release.

TABLE I Events Event Trigger Event Source Event Notification Emptycontainer Empty Container Released by Carrier Carrier's system or Nonepick-up CC System Empty container Arrival of container at Shipper'sCarrier's system or None positioned premises CC System DepartureDeparture of Container from a Location Carrier's system or Yes, if notnotified CC System to CC System Arrival Arrival of Container at LocationCarrier's system or Yes, if not notified CC System to CC System Loadedon Truck As part of an inland move, container has Carrier's system orNone been loaded onto a Truck CC System Loaded on Rail As part of aninland move, container has Carrier's system or None been loaded onto atrain CC System Loaded on Barge As part of an inland move, container hasCarrier's system or None been loaded onto a barge CC System Loaded onContainer has been loaded onto a vessel Carrier's system or None VesselCC System Discharged from Container has been unloaded from Carrier'ssystem or None Vessel vessel CC System Customs Container has clearedcustoms Carrier's System or Yes Clearance nominated agent's system or CCSystem Customs Hold Container has been held at Customs Carrier's Systemor Yes nominated agent's system or CC System Customs Release Containerhas been released by Customs Carrier's System or Yes after being heldnominated agent's system or CC System Cargo Release Cargo has beenreleased by the Carrier Carrier's system or None CC System Free Time toContainers from time about to expire Carrier's system or Yes Expire CCSystem Free Time Container free time has expired Carrier's system or YesExpired CC System

FIG. 13 illustrates the flow of messages sent and received by the commoncarrier system. EDI may be received in all EDI formats. Carriers may,for example, send 301 document message types to confirm containerbooking. Carriers may, for example, send document type 315 status eventsto the common carrier system to update container status. Events may be,for example and without limitation, anything from pick up at shipper, toocean voyage through customs clearance to ultimate delivery. Carriersmay send a range of different messages. Finally, the common carriersystem supports but is not limited to EDI, XML, email and the like tosend out received messages to the users.

Thus, has been described a system that enables domestic and/orinternational transportation users to handle shipping transactionsthrough a single common system substantially through a neutraltransportation portal. The system provides, among other things,transportation users with single point of entry for tracking cargomovements with multiple carriers. The system also gives users access toscheduling, booking requests for booking cargo across several carriersand proactive event notification. Many variation and alterations of theembodiments are of course possible.

1. A system for creating booking requests pertaining to informationrelating to the transport of a container, said information including atleast one of a carrier name, departure date, departure time, departurelocation, arrival date, arrival time, arrival location, origin, anddestination, the system comprising: a plurality of entities registeredwith the system, each entity having a computer storage, each of theentities configured to communicate with users over a first communicationpathway to establish a shipping rate pertaining to the shipment ofcontainers using a given entity and generate a contract reference; and aserver at a second entity that is configured to receive information fromsaid computer storage of said plurality of entities over a secondcommunication pathway and provide a computer user interface for displayon a user's computer over a third communication pathway, the computeruser interface including a field configured to receive the contractreference, said server configured to receive from a user over the thirdcommunication pathway an electronic booking request including theinformation relating to the transport of a container, said serverincluding a storage configured to store templates of electronic bookingrequests and provide one of said templates based on a search oftemplates performed by said user, said electronic booking requestreceived over the third communication pathway having been created fromone of said stored templates, said server further configured to transmitsaid electronic booking request including the contract reference to atleast a first entity of said plurality of entities over the secondcommunication pathway, wherein the contract reference pertains to theestablished shipping rate between at least the first entity and theuser.
 2. The system according to claim 1, wherein the template wascreated by the user prior to the creation of the electronic bookingrequest.
 3. The system according to claim 1, wherein the electronicbooking request is created from a previously drafted electronic bookingstored on the system.
 4. The system according to claim 3, wherein thepreviously drafted electronic booking was a confirmed electronic bookingrequest that was confirmed by at least one of the plurality of entitiesregistered with the system prior to the user or the any other usercreating the electronic booking request.
 5. The system according toclaim 1, wherein the electronic booking request further includesinformation regarding the container being transported from an inlandorigin to a first vessel, the container being loaded onto the firstvessel, the container being transported by the first vessel to alocation, the container being discharged from the first vessel, and thecontainer being delivered to a destination.
 6. The system according toclaim 1, wherein the user is a new customer of the first entity.
 7. Thesystem of claim 1, wherein the electronic booking request comprises arouting request.
 8. The system of claim 7, wherein the confirmation ofthe electronic booking request comprises routing information.
 9. Thesystem of claim 1, wherein the user interface is further configured toreceive shipping instructions from the user over the third communicationpathway, said server further configured to send the shippinginstructions combined with the booking request to the first entity overthe second communication pathway.
 10. The system of claim 1, wherein theuser interface is further configured to enable the user to receive abooking activity plan from the first entity over the secondcommunication pathway.
 11. The system of claim 10, wherein theconfirmation of the electronic booking request further comprises thebooking activity plan.
 12. The system of claim 10, wherein the bookingactivity plan further comprises transport modes, transhipment locations,and interim arrival and departure dates and times.
 13. The system ofclaim 1, wherein the electronic booking request includes ExtensibleMarkup Language (XML).
 14. The system of claim 1, wherein the server isconfigured to receive the electronic booking request via Electronic DataInterchange (EDI).
 15. The system of claim 1, wherein the server isconfigured to receive the electronic booking request via website. 16.The system of claim 1, wherein the server is configured to receive theelectronic booking request via electronic mail.
 17. The system of claim1, wherein the server is configured to transmit confirmation of theelectronic booking request to the user via Electronic Data Interchange(EDI).
 18. The system of claim 1, wherein the server is configured totransmit confirmation of the electronic booking request to the user viaelectronic mail.
 19. The system of claim 1, wherein the server isconfigured to transmit confirmation of the electronic booking requestsuch that the confirmation is configured to be displayed to the user viaa pop-up dialogue box.
 20. The system according to claim 1, wherein saidserver forwards said request to at least said first entity of saidplurality of entities.
 21. The system of claim 1, wherein the userinterface further enables the user to send shipping instructions to thefirst entity through the server after the user has received confirmationof said booking request from the server.
 22. A system for creatingbooking requests pertaining to information relating to the transport ofa container, said information including at least one of a carrier name,departure date, departure time, departure location, arrival date,arrival time, arrival location, origin, and destination, the systemcomprising: a plurality of entities registered with the system, eachentity having a computer storage, each of the entities configured tocommunicate with users over a first communication pathway to establish ashipping rate pertaining to the shipment of a quantity of containersusing a given entity and generating a contract reference; and a serverconfigured to receive information from a computer storage of a firstentity of said plurality of entities over a second communication pathwayand provide a computer user interface for display on a user's computerover a third communication pathway, the computer user interfaceincluding a field configured to receive the contract reference, theserver configured to receive from a user over the third communicationpathway an electronic booking request including the information relatingto the transport of a container, said server including a storageconfigured to store templates of electronic booking requests and provideone of said templates based on a search of templates performed by saiduser, said electronic booking request received over the thirdcommunication pathway having been created from one of said storedtemplates, said server further configured to transmit said electronicbooking request including the contract reference to at least the firstentity over the second communication pathway, wherein the contractreference pertains to the established shipping rate between at least thefirst entity and the user, wherein the system, responsive toconfirmation from the first entity to the user and registered entitydata, is configured to generate electronic event notification messages.23. The system according to claim 22, wherein the server is configuredto receive an indication from the user over the third communicationpathway that is used to determine when the system should notify the userof an event.
 24. The system according to claim 23, wherein the event isa non-event.
 25. The system according to claim 24, wherein the system isconfigured to notify the user of the non-event over the thirdcommunication pathway after a predetermined time period has lapsed andthe event has not occurred such that the server is configured to set thepredetermined time period based on user designation.
 26. The system ofclaim 22, wherein the server is configured to generate the electronicevent notification messages using electronic mail.
 27. The system ofclaim 22, wherein the server is configured to transmit electronic eventnotification messages that are displayed to the user via pop-up dialogueboxes.
 28. The system of claim 22, wherein the server is configured togenerate electronic event notification messages using EDI.
 29. Thesystem according to claim 22, wherein said server forwards said requestto said at least first entity.
 30. A system for creating bookingrequests pertaining to information relating to the transport of acontainer, said information including at least one of a carrier name,departure date, departure time, departure location, arrival date,arrival time, arrival location, origin, and destination, the systemcomprising: a first computer storage located at a first carrierregistered with the system; a second computer storage located at asecond carrier registered with the system, the first and second carriersconfigured to communicate with users over a first communication pathwayto establish a shipping rate pertaining to the shipment of a quantity ofcontainers using a given entity and generate a contract reference; and aserver that receives information from said first storage and said secondstorage over a second communication pathway, said server configured toprovide a computer user interface for display on a user's computer overa third communication pathway, the computer user interface including afield configured to receive the contract reference, the serverconfigured to receive from a user over the third communication pathwayan electronic booking request including the information relating to thetransport of a container, and to transmit said electronic bookingrequest to at least one of the first and second carriers, saidelectronic booking request including information relating to thetransport of a container, said server including a storage configured tostore templates of electronic booking requests and provide one of saidtemplates based on a search of templates performed by said user, saidelectronic booking request received over the third communication pathwayhaving been created from one of said stored templates, said serverconfigured: to receive a routing request from the user over the thirdcommunication pathway and to transmit the routing request to at leastone of the first and second carriers over the second communicationpathway; to receive shipping instructions from the user over the thirdcommunication pathway and to transmit said instructions to at least oneof the first and second carriers over the second communication pathway;to receive a confirmation of the electronic booking request from atleast one of the first and second carriers over the second communicationpathway and to transmit the confirmation to the user over the thirdcommunication pathway; to receive routing information from at least oneof the first and second carriers over the second communication pathwayand to transmit the routing information to the user over the thirdcommunication pathway; and to receive a booking activity plan from atleast one of the first and second carriers over the second communicationpathway and to transmit the booking activity plan to the user over thethird communication pathway, wherein the booking activity plan includestransport modes, transhipment locations, and interim arrival anddeparture dates and times.
 31. The system according to claim 30, whereinsaid server forwards said request to said at least one of the first andsecond carriers.
 32. A system for creating booking requests pertainingto information relating to the transport of a container, saidinformation including at least one of a carrier name, departure date,departure time, departure location, arrival date, arrival time, arrivallocation, origin, and destination, the system comprising: a firststorage located at a user registered with the system; a second storagelocated at a carrier registered with the system, the carrier configuredto communicate with the user over a first communication pathway toestablish a shipping rate pertaining to the shipment of a quantity ofcontainers using a given entity and generate a contract reference; and aserver including a storage configured to store templates of electronicbooking requests and provide one of said templates based on a search oftemplates performed by said user, said server configured: to receive anelectronic booking request sent from the first storage over a secondcommunication pathway, said electronic booking request includinginformation relating to the transport of a container, said electronicbooking request including a field corresponding to a contract referencepertaining to an established shipping rate between the user and thecarrier, said electronic booking request having been created from one ofsaid stored templates, to store the electronic booking request includingthe contract reference field, to transmit information relating to saidelectronic booking request to the second storage over a thirdcommunication pathway, wherein the electronic booking request includes arequest to transport one or more containers, to receive information fromsaid carrier relating to said request over the third communicationpathway, and to forward a message to said user over the secondcommunication pathway based on said information received from saidcarrier regarding said request.
 33. The system of claim 32, wherein theelectronic booking request comprises an Electronic Data Interchange(EDI) message.
 34. The system of claim 32, wherein the electronicbooking request comprises an XML message.
 35. The system of claim 32,wherein the server is configured to sent the electronic booking requestto the second storage over the third communication pathway usingElectronic Data Interchange (EDI).
 36. The system of claim 32, whereinthe server receives a confirmation of the electronic booking requestfrom the carrier over the third communication pathway as at least partof said information.
 37. The system of claim 36, wherein theconfirmation of the electronic booking request comprises routinginformation.
 38. The system of claim 36, wherein the confirmation of theelectronic booking request comprises a carrier booking number.
 39. Thesystem of claim 32, wherein the server is further configured to receivea booking activity plan from the carrier over the third communicationpathway and to use the booking activity plan to provide containertracking services to the user over the second communication pathway. 40.The system of claim 32, wherein the server is further configured tomodify a booking after physical movement of the one or more containershas begun.
 41. The system according to claim 32, wherein said serverforwards said electronic booking request to said at least one of thefirst and second carriers.